Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1224

reference
736-tree-1
name
1224
tree-preservation-order

undefined

736-tpo-1
uprn
address-text
point
POINT (-1.009294 50.886077)
geometry
MULTIPOLYGON (((-1.009195 50.886066,-1.009200 50.886085,-1.009213 50.886103,-1.009235 50.886117,-1.009263 50.886126,-1.009293 50.886130,-1.009324 50.886127,-1.009352 50.886118,-1.009374 50.886104,-1.009389 50.886087,-1.009394 50.886068,-1.009390 50.886048,-1.009376 50.886031,-1.009354 50.886016,-1.009327 50.886007,-1.009296 50.886004,-1.009265 50.886007,-1.009237 50.886015,-1.009215 50.886029,-1.009200 50.886047,-1.009195 50.886066)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL